Supporting interworking and/or mobility between different wireless communication systems

ABSTRACT

There is provided a method performed by a network unit, and a corresponding network unit as well as a corresponding wireless communication device, for supporting interworking and/or idle mode mobility between different wireless communication systems, including a higher generation wireless system and a lower generation wireless system, to enable secure communication with the wireless communication device. The method comprises selecting, in connection with a registration procedure and/or a security context activation procedure of the wireless communication device with the higher generation wireless system, at least one security algorithm of the lower generation wireless system, also referred to as lower generation security algorithm(s). The method also comprises sending a control message including information on the selected lower generation security algorithm(s) to the wireless communication device. The method further comprises storing information on the selected lower generation security algorithm(s) in the network unit.

CROSS REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of U.S. patentapplication Ser. No. 16/332,973, filed Mar. 13, 2019, granted as U.S.Pat. No. 11,418,961 on Aug. 16, 2022, which is a 35 U.S.C. § 371National Stage of International Patent Application No.PCT/EP2019/052618, filed Feb. 4, 2019, designating the United States andclaiming priority to U.S. provisional application No. 62/632,072, filedon Feb. 19, 2018. The above identified applications are incorporated byreference.

TECHNICAL FIELD

The proposed technology generally relates to mechanisms for supportinginterworking and/or mobility between different wireless communicationsystems, especially between different generations of wirelesscommunication systems including a higher generation wireless system anda lower generation wireless system, and more specifically concernsmethods, network units, wireless communication devices, as well ascorresponding computer programs and computer-program products andapparatuses.

BACKGROUND

Wireless communication systems are constantly evolving and intenseresearch and development takes place at all over the world.

There is now a wide variety of different types and/or generations ofwireless communication systems and technologies, such as UniversalMobile Telecommunications System (UMTS), Long Term Evolution (LTE) andNew Generation (NG), sometimes referred to as 3G/4G and 5G.

It may be useful to start with a very brief overview of the UniversalMobile Telecommunications System (UMTS) architecture, sometimes alsoreferred to as 3G, and the Long Term Evolution (LTE) architecture alsoreferred to as 4G.

To start with, the Radio Access Network (RAN) part of the architecturesdiffers in that Universal Terrestrial Radio Access Network (UTRAN) isthe 3G/UMTS RAN and Evolved UTRAN (E-UTRAN) is the LTE RAN. UTRANsupports both circuit switched and packet switched services whileE-UTRAN only supports packet switched services.

The UTRAN air interface is Wideband Code Division Multiple Access(WCDMA) based on spread spectrum modulation technology while E-UTRANemploys a multi-carrier modulation scheme called Orthogonal FrequencyDivision Multiple Access (OFDMA). High Speed Packet Access (HSPA) is aset of protocols that extend and improve the performance of existing 3GUMTS networks using the WCDMA protocol.

In 3G/UMTS, the RAN is based on two types of nodes: the access node orbase station called NodeB and the Radio Network Controller (RNC). TheRNC is the node controlling the RAN, and it also connects the RAN to theCore Network (CN).

FIG. 1 is a schematic diagram illustrating a simplified overview of thecore network for UMTS. The core network for UMTS/WCDMA includes:

the Circuit-Switched (CS) domain with the Mobile Switching Center (MSC)for connection to the Public Switched Telephone Network (PSTN);

the Packet-Switched (PS) domain with the Serving GPRS Support Node(SGSN) for connection to the RAN, and the Gateway GPRS Support Node(GGSN) for connection to external networks, such as the Internet.

Common for the two domains is the Home Location register (HLR), adatabase in the home operator's network that keeps track of thesubscribers of the operator.

A key design philosophy of the LTE RAN is to use only one type of node,the evolved Node B, also referred to as eNodeB or eNB. A key concept ofthe LTE CN is to be independent of the radio access technology to theextent possible.

The LTE RAN functions usually involve:

Coding, interleaving, modulation and other typical physical layerfunctions;

Automatic Repeat request (ARQ) header compression and other typical linklayer functions;

User Plane (UP) security functions, e.g., ciphering, and RAN signalingsecurity, e.g., ciphering and integrity protection of RAN originatedsignaling to the UE; and

Radio Resource Management (RRM), handover, and other typical radioresource control functions.

The LTE CN functions usually involve:

Non-Access Stratum (NAS) security functions, e.g. ciphering andintegrity protection of CN signaling to the UE;

Subscriber management;

Mobility management;

Bearer management and Quality of Service (QoS) handling;

Policy control and user data flows;

Interconnection to external networks.

The evolution and standardization of the LTE CN was called the SystemArchitecture Evolution (SAE) and the core network defined in SAE differsradically from the older generation core network and was therefore namedthe Evolved Packet Core (EPC).

FIG. 2 is a schematic diagram illustrating a simplified overview of theEPC architecture. The basic nodes of the EPC include:

the Mobility Management Entity (MME), which is the control plane node ofthe EPC;

the Serving Gateway (SG), which is the user plane node connecting theEPC to the LTE RAN; and

the Packet Data Network Gateway (PDN) Gateway, which is the user planenode connecting the EPC to the Internet.

The MME is normally also connected to a Home Subscriber Server (HSS),which is a database node corresponding to the HLR.

The Serving Gateway and the PDN Gateway may be configured as a singleentity.

Sometimes the EPC together with the LTE RAN is denoted Evolved PacketSystem (EPS).

Currently, the future generation of wireless communications, commonlyreferred to as Next Generation (NextGen or NG), Next Generation System(NGS) or 5G, is being developed all over the world, although no common5G standard has yet been finally set.

The vision of Next Generation wireless communications lies in providingvery high data rates, extremely low latency, a manifold increase in basestation capacity, and significant improvements of user perceived QoS,compared to current 4G LTE networks.

3GPP is currently developing the standards for 5G. It is expected that5G will support many new scenarios and use cases and will be an enablerfor the Internet of Things, IoT. It is expected that NG systems willprovide connectivity to a wide range of new devices such as sensors,smart wearables, vehicles, machines, and so forth. Flexibility wouldthen be a key property in NG Systems. This is reflected in the securityrequirement for network access that are mandating the support ofalternative authentication methods and different types of credentialsthan the usual Authentication and Key Agreement, AKA, credentialspre-provisioned by the operator and securely stored in the UniversalIntegrated Circuit Card, UICC or similar device. This would allowfactory owners or enterprises to leverage their own identity andcredential management systems for authentication and access networksecurity.

The 3GPP architecture working group has finalized the architecture of 5GSystems illustrated in FIG. 3 . For more information, reference can bemade to TS 23.501.

The Access and Mobility management Function (AMF), sometimes referred toas the Mobility Management Function, MMF, Core Network MobilityManagement (CN-MM) or simply Mobility Management (MM), is the networkunit or node that supports mobility management and is, thus, playing asimilar role to the MME in EPC. AMF has a so-called NG2 interface to RANthat corresponds to the so-called S1 interface between MME and RAN inEPC.

In general, mobility management involves handling UEs in both idle modeand connected mode.

Idle mode mobility in 5G/NGS will probably be a special case of theRegistration procedure, e.g. see clause 4.2.2.2.2 in v0.1.1 draft 3GPPTS 23.502. In the Registration procedure, User Equipment (UE) needs toregister with the network to get authorized to receive services, toenable mobility tracking and to ensure reachability. The Registrationprocedure is used e.g. when the UE needs to initially register to the 5Gsystem, upon mobility procedures when the UE changes to a new TrackingArea (TA) in idle mode and when the UE performs a periodic update (dueto a predefined time period of inactivity), and so forth.

5G/NGS also allows idle mode mobility from 5G/NGS to 4G/EPS. When a UEmoves out of 5G/NGS coverage into 4G/EPS coverage, it will have a 5G/NGSsecurity context, but may not have a 4G/EPS security context.

In order to guarantee a smooth deployment of the 5G Systems, the 3GPParchitecture group is currently working on the support of interworkingbetween 3G/4G (legacy) and 5G Systems. This will allow not only idlemobility between the systems but also handovers.

Interworking involves network entities and data objects belonging todifferent generation systems. The architecture for interworking is givenin FIG. 4 . For more information, reference can be made to TS 23.501.

The general principle has been to adapt to the older generation in orderto minimize impact on legacy infrastructure and ensure a smoothdeployment of the new one, and the security mechanisms for interworkingshould minimize, if not possible to avoid, impact on 3G/4G.

Consequently, the newer generation must adapt to the older generation.Nevertheless, this should not incur restrictions or constraints on the5G security mechanisms outside of interworking. More precisely,interworking with 3G/4G should not prevent the independent evolution of5G security, e.g. introducing new crypto algorithms, increasing the sizeof the MAC fields, etc. In other terms, the security mechanisms forinterworking should not prevent the independent evolution of 5Gsecurity.

Now, one of the basic security requirements when introducing newfeatures is that they should not break or weaken the security of theoverall system. In fact, across generations, the trend has been that thesecurity level did improve. Therefore, the security mechanisms forinterworking should maintain at least the same level of securitycompared to 3G/4G. This does not overrule the introduction ofimprovements.

The security working group of 3GPP called SA3 is currently working onthe security mechanisms for interworking between EPS and 5GS. One of themain working assumptions is that there shall be no impact on the MME. Sofrom the MME perspective, it is communicating with another MME.Therefore, during idle mode mobility, e.g. from 5GS to 4GS, the sourceAMF should mimic the behavior of a source MME during a Tracking AreaUpdate procedure (TAU) as described in TS 33.401.

In EPS, during a Tracking Area Update procedure, the target MME receivesthe UE security context from the source MME. The security contextincludes the necessary parameters to secure the Non-Access Stratum, NAS,protocol, i.e. anchor key KASME and NAS integrity and confidentialitykeys and selected NAS security algorithms. The target MME may directlyactivate NAS security so that all the NAS message with the UE areprotected once the security context is received from the source node. Ifthe target MME is configured to run other NAS algorithms, it may thenrun a NAS Security Mode Command (NAS SMC) procedure to select otheralgorithms and to signal the new selection to the UE.

Now the current description in TS 33.501 [2] indicates that the sourceAMF generates a mapped EPS security context from the current 5G securitycontext and delivers it to the target MME. The problem now is which EPSalgorithms are to be selected so that the MME can activate the NASsecurity directly without the need for a NAS SMC procedure. Observe thataccording to the legacy behavior a NAS SMC run is only required toselect other algorithms. So the core of the issue is the selection ofthe NAS algorithm to be used with EPS.

Two solutions were proposed. Solution (A) is based on selecting void NASalgorithms values so that the target MME is forced to perform a NAS SMCto select new algorithms. More precisely, in the current standards,there are specific values that are reserved for future use, e.g. for newalgorithms. This is what is referred to as void values. Solution (B) isbased on using a predefined algorithm mapping table included in thestandards.

Solution (B) would require continuous standard updates, should newalgorithms be introduced for LTE or NR. Solution (A) seems more like atemporary work around and not a proper security design. In addition,using some of the existing undefined values to indicate that no validalgorithms are selected rules them out automatically from beingcandidates when new algorithms are introduced.

SUMMARY

It is an object to provide improved mechanism for supportinginterworking and/or mobility between different wireless communicationsystems, especially between different generations of wirelesscommunication systems including a higher generation wireless system anda lower generation wireless system.

It is also an object to provide a method, performed by a network unit,for supporting interworking between different wireless communicationsystems.

Another object is to provide a method, performed by a network unit, forsupporting idle mode mobility of a wireless communication device betweendifferent wireless communication systems.

Yet another object is to provide a method, performed by a wirelesscommunication device, for supporting interworking between differentwireless communication systems.

Another object is to provide a network unit configured to supportinterworking between different wireless communication systems.

Yet another object is to provide a wireless communication deviceconfigured to support interworking between different wirelesscommunication systems.

Still another object is to provide computer programs for supporting,when executed by a processor, interworking between different wirelesscommunication systems, and corresponding computer-program products.

It is also an object to provide apparatuses for supporting interworkingbetween different wireless communication systems.

These and other objects are met by embodiments of the proposedtechnology.

According to a first aspect, there is provided a method, performed by anetwork unit, for supporting interworking between different wirelesscommunication systems, including a higher generation wireless system anda lower generation wireless system, to enable secure communication witha wireless communication device, wherein the method comprises:

selecting, in connection with a registration procedure and/or a securitycontext activation procedure of the wireless communication device withthe higher generation wireless system, at least one security algorithmof the lower generation wireless system, also referred to as lowergeneration security algorithm(s);

sending a control message including information on the selected lowergeneration security algorithm(s) to the wireless communication device;and

storing information on the selected lower generation securityalgorithm(s) in the network unit.

According to a second aspect, there is provided a method, performed by anetwork unit, for supporting idle mode mobility of a wirelesscommunication device between different wireless communication systems,including a higher generation wireless system and a lower generationwireless system, wherein the method comprises:

selecting, in connection with a registration procedure and/or a securitycontext activation procedure of the wireless communication device withthe higher generation wireless system, at least one security algorithmof the lower generation wireless system, also referred to as lowergeneration security algorithm(s);

sending a control message including information on the selected lowergeneration security algorithm(s) to the wireless communication device;and

storing information on the selected lower generation securityalgorithm(s) in the network unit.

According to a third aspect, there is provided a method, performed by awireless communication device, for supporting interworking betweendifferent wireless communication systems, including a higher generationwireless system and a lower generation wireless system, to enable securecommunication for the wireless communication device, wherein the methodcomprises:

receiving, in connection with a registration procedure and/or a securitycontext activation procedure of the wireless communication device withthe higher generation wireless system, a control message includinginformation on at least one security algorithm of the lower generationwireless system, also referred to as lower generation securityalgorithm(s);

storing information on the selected lower generation securityalgorithm(s) in the wireless communication device.

According to a fourth aspect, there is provided a network unitconfigured to support interworking between different wirelesscommunication systems, including a higher generation wireless system anda lower generation wireless system, to enable secure communication witha wireless communication device,

wherein the network unit is configured to select, in connection with aregistration procedure and/or a security context activation procedure ofthe wireless communication device with the higher generation wirelesssystem, at least one security algorithm of the lower generation wirelesssystem, also referred to as lower generation security algorithm(s);

wherein the network unit is configured to send a control messageincluding information on the selected lower generation securityalgorithm(s) to the wireless communication device; and

wherein the network unit is configured to store information on theselected lower generation security algorithm(s) in the network unit.

According to a fifth aspect, there is provided a wireless communicationdevice configured to support interworking between different wirelesscommunication systems, including a higher generation wireless system anda lower generation wireless system, to enable secure communication forthe wireless communication device,

wherein the wireless communication device is configured to receive, inconnection with a registration procedure and/or a security contextactivation procedure of the wireless communication device with thehigher generation wireless system, a control message includinginformation on at least one security algorithm of the lower generationwireless system, also referred to as lower generation securityalgorithm(s);

wherein the wireless communication device is configured to storeinformation on the selected lower generation security algorithm(s) inthe wireless communication device.

According to a sixth aspect, there is provided a computer program forsupporting, when executed by a processor, interworking between differentwireless communication systems, including a higher generation wirelesssystem and a lower generation wireless system, to enable securecommunication with a wireless communication device, wherein the computerprogram comprises instructions, which when executed by the processor,cause the processor to:

select, in connection with a registration procedure and/or a securitycontext activation procedure of the wireless communication device withthe higher generation wireless system, at least one security algorithmof the lower generation wireless system, also referred to as lowergeneration security algorithm(s);

generate a control message including information on the selected lowergeneration security algorithm(s) for transmission to the wirelesscommunication device; and

store information on the selected lower generation securityalgorithm(s).

According to a seventh aspect, there is provided a computer-programproduct comprising a computer-readable medium carrying such a computerprogram.

According to an eighth aspect, there is provided a computer program forsupporting, when executed by a processor, interworking between differentwireless communication systems, including a higher generation wirelesssystem and a lower generation wireless system, to enable securecommunication for a wireless communication device, wherein the computerprogram comprises instructions, which when executed by the processor,cause the processor to:

receive, in connection with a registration procedure and/or a securitycontext activation procedure of the wireless communication device withthe higher generation wireless system, a control message includinginformation on at least one security algorithm of the lower generationwireless system, also referred to as lower generation securityalgorithm(s);

store information on the selected lower generation security algorithm(s)in the wireless communication device.

According to a ninth aspect, there is provided a computer-programproduct comprising a computer-readable medium carrying such a computerprogram.

According to a tenth aspect, there is provided an apparatus forsupporting interworking between different wireless communicationsystems, including a higher generation wireless system and a lowergeneration wireless system, to enable secure communication with awireless communication device, wherein the apparatus comprises:

a selection module for selecting, in connection with a registrationprocedure and/or a security context activation procedure of the wirelesscommunication device with the higher generation wireless system, atleast one security algorithm of the lower generation wireless system,also referred to as lower generation security algorithm(s);

a generating module for generating a control message includinginformation on the selected lower generation security algorithm(s) fortransmission to the wireless communication device; and

a storage module for storing information on the selected lowergeneration security algorithm(s) in the network unit.

According to an eleventh aspect, there is provided an apparatus forsupporting interworking between different wireless communicationsystems, including a higher generation wireless system and a lowergeneration wireless system, to enable secure communication for awireless communication device, wherein the apparatus comprises:

a receiving module for receiving, in connection with a registrationprocedure and/or a security context activation procedure of the wirelesscommunication device with the higher generation wireless system, acontrol message including information on at least one security algorithmof the lower generation wireless system, also referred to as lowergeneration security algorithm(s);

a storage module for storing information on the selected lowergeneration security algorithm(s) in the wireless communication device.

According to a twelfth aspect, there is provided a network unitconfigured to support idle mode mobility of a wireless communicationdevice between different wireless communication systems, including ahigher generation wireless system and a lower generation wirelesssystem,

wherein the network unit is configured to select, in connection with aregistration procedure and/or a security context activation procedure ofthe wireless communication device with the higher generation wirelesssystem, at least one security algorithm of the lower generation wirelesssystem, also referred to as lower generation security algorithm(s);

wherein the network unit is configured to send a control messageincluding information on the selected lower generation securityalgorithm(s) to the wireless communication device; and

wherein the network unit is configured to store information on theselected lower generation security algorithm(s) in the network unit.

In this way, there is provided an improved solution for supportinginterworking and/or mobility between wireless communication systems ofdifferent generations.

For example, there is provided a security solution for supportinginterworking between wireless communication systems of differentgenerations, such as 5G and 4G, that removes the need for a separatesecurity activation procedure, such as the NAS SMC procedure, with thetarget system during idle mode mobility.

Rather, the selection of the security algorithms for the target systemmay be performed and signaled already during security establishment inthe source system when the selection and negotiation of the securityalgorithms for the source system takes place.

Other advantages will be appreciated when reading the detaileddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments, together with further objects and advantages thereof,may best be understood by making reference to the following descriptiontaken together with the accompanying drawings, in which:

FIG. 1 is a schematic diagram illustrating a simplified overview of thecore network for UMTS.

FIG. 2 is a schematic diagram illustrating a simplified overview of theEPC architecture.

FIG. 3 is a schematic diagram illustrating an example of the non-roamingarchitecture for 5G/NGS.

FIG. 4 is a schematic diagram illustrating an example of an architecturefor interworking between wireless systems of different generations.

FIG. 5A is a schematic diagram illustrating an example of two differentwireless communication systems capable of interworking according to anembodiment.

FIG. 5B is a schematic flow diagram illustrating an example of a methodfor a method, performed by a network unit, for supporting interworkingand/or idle mode mobility between different wireless communicationsystems.

FIG. 5C is a schematic flow diagram illustrating another example of amethod for a method, performed by a network unit, for supportinginterworking and/or idle mode mobility between different wirelesscommunication systems.

FIG. 5D is a schematic flow diagram illustrating yet another example ofa method for a method, performed by a network unit, for supportinginterworking and/or idle mode mobility between different wirelesscommunication systems.

FIG. 6A is a schematic flow diagram illustrating an example of a method,performed by a wireless communication device, for supportinginterworking between different wireless communication systems.

FIG. 6B is a schematic flow diagram illustrating another example of amethod, performed by a wireless communication device, for supportinginterworking between different wireless communication systems.

FIG. 7 is a schematic diagram illustrating an example of a NAS SMCprocedure with 4GS/EPS algorithm selection according to an embodiment.

FIG. 8 is a schematic diagram illustrating an example of usage ofpreselected 4GS/EPS algorithm(s) during idle mode mobility from 5GS/NGSto 4GS/EPS.

FIG. 9 is a schematic diagram illustrating an example of a NAS SMCprocedure with TAU protection indication according to an embodiment.

FIG. 10 is a schematic diagram illustrating an example of usage of TAUprotection indication during idle mode mobility from 5GS/NGS to 4GS/EPS.

FIG. 11A is a schematic block diagram illustrating an example of anarrangement such as a network unit and/or wireless communication deviceconfigured to support interworking between different wirelesscommunication systems according to an embodiment.

FIG. 11B is a schematic block diagram illustrating an example of anarrangement such as a network unit and/or wireless communication deviceconfigured to support interworking between different wirelesscommunication systems according to another embodiment.

FIG. 11C is a schematic block diagram illustrating an example of anarrangement such as a network unit and/or wireless communication deviceconfigured to support interworking between different wirelesscommunication systems according to yet another embodiment.

FIG. 12 is a schematic diagram illustrating an example of acomputer-implementation according to an embodiment.

FIG. 13 is a schematic diagram illustrating an example of an apparatusfor supporting interworking between different wireless communicationsystems.

FIG. 14 is a schematic diagram illustrating an example of an apparatusfor supporting interworking between different wireless communicationsystems.

FIG. 15 schematically illustrates a distributed implementation amongnetwork devices.

FIG. 16 is a schematic diagram illustrating an example of a wirelessnetwork in accordance with some embodiments.

FIG. 17 is a schematic diagram illustrating an example of an embodimentof a UE in accordance with various aspects described herein.

FIG. 18 is a schematic block diagram illustrating an example of avirtualization environment in which functions implemented by someembodiments may be virtualized.

FIG. 19 is a schematic diagram illustrating an example of atelecommunication network connected via an intermediate network to ahost computer in accordance with some embodiments.

FIG. 20 is a schematic diagram illustrating an example of a hostcomputer communicating via a base station with a user equipment over apartially wireless connection in accordance with some embodiments.

FIGS. 21A-B are schematic flow diagrams illustrating examples of methodsimplemented in a communication system including, e.g. a host computer,and optionally also a base station and a user equipment in accordancewith some embodiments.

FIGS. 22A-B are schematic diagrams illustrating examples of methodsimplemented in a communication system including a host computer, a basestation and a user equipment in accordance with some embodiments.

DETAILED DESCRIPTION

Throughout the drawings, the same reference numbers are used for similaror corresponding elements.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

The proposed technology generally relates to mechanisms for supportinginterworking and/or mobility between different wireless communicationsystems, especially between different generations of wirelesscommunication systems including a higher generation wireless system anda lower generation wireless system. From context, a higher generationwireless system and a lower generation wireless system are clear to theskilled person, keeping in mind that different generations of wirelesscommunication systems may include 5G, 4G and/or 3G systems.

In the following, the general non-limiting term “network unit” may referto any network unit suitable for operation in connection with a wirelesscommunication system, including but not limited to network devices,network nodes and/or similar devices.

As used herein, the term “network device” may refer to any devicelocated in connection with a communication network, including but notlimited to devices in access networks, core networks and similar networkstructures. The term network device may also encompass computer-basednetwork devices such as cloud-based network devices for implementationin cloud-based environments.

As used herein, the non-limiting term “network node” may refer to anynetwork node in a communication system including network nodes in accessnetworks, core networks and similar network structures.

As used herein, the non-limiting terms “wireless communication device”,“User Equipment (UE)”, and “terminal” may refer to a mobile phone, acellular phone, a Personal Digital Assistant (PDA), equipped with radiocommunication capabilities, a smart phone, a laptop or Personal Computer(PC), equipped with an internal or external mobile broadband modem, atablet with radio communication capabilities, a target device, a deviceto device UE, a machine type UE or UE capable of machine to machinecommunication, Customer Premises Equipment (CPE), Laptop EmbeddedEquipment (LEE), Laptop Mounted Equipment (LME), USB dongle, a portableelectronic radio communication device, a sensor device equipped withradio communication capabilities or the like. In particular, the term“wireless communication device” should be interpreted as a non-limitingterm comprising any type of wireless device communicating with a networknode in a wireless communication system and/or possibly communicatingdirectly with another wireless communication device. In other words, awireless communication device may be any device equipped with circuitryfor wireless communication according to any relevant standard forcommunication.

It may be useful to start with a brief overview of interworking wirelesscommunication systems.

FIG. 5A is a schematic diagram illustrating an example of two differentwireless communication systems capable of interworking according to anembodiment. In this example, there is provided a schematic overview ofan architecture for supporting interworking and/or idle mode mobilitybetween different wireless communication systems, including a highergeneration wireless system 40 and a lower generation wireless system 50,to enable secure communication with a wireless communication device 30.The higher generation wireless system 40 may include one or more networkunits 10 cooperating with a corresponding higher generation radio accessnetwork (RAN) 15 to provide wireless communication services to thewireless communication device 30. Similarly, the lower generationwireless system 50 may include one or more network units 20 cooperatingwith a corresponding lower generation radio access network (RAN) 25 toprovide wireless communication services to the wireless communicationdevice 30. The network unit(s) 10 of the higher generation wirelesssystem 40 and the network unit(s) 20 of the lower generation wirelesssystem 50 may be directly and/or indirectly interconnected to enableefficient exchange of information for supporting interworking and/ormobility.

FIG. 5B is a schematic flow diagram illustrating an example of a methodfor a method, performed by a network unit, for supporting interworkingand/or idle mode mobility between different wireless communicationsystems, including a higher generation wireless system and a lowergeneration wireless system, to enable secure communication with awireless communication device.

Basically, the method comprises:

-   S1: selecting, in connection with a registration procedure and/or a    security context activation procedure of the wireless communication    device with the higher generation wireless system, at least one    security algorithm of the lower generation wireless system, also    referred to as lower generation security algorithm(s);-   S2: sending a control message including information on the selected    lower generation security algorithm(s) to the wireless communication    device; and-   S3: storing information on the selected lower generation security    algorithm(s) in the network unit.

Sometimes the expression security context activation procedure isreferred to as a security activation procedure for a wirelesscommunication device.

A security context normally includes at least one security key, possiblytogether with optional related information such as one or more freshnessparameters and/or information on security algorithms that can be used.

For example, the method may be performed by a network unit 10 of thehigher generation wireless system 40 when the wireless communicationdevice 30 registers and initiates establishment of a security contextwith the higher generation wireless system 40.

By way of example, the network unit 10 of the higher generation wirelesssystem 40 may be a core network unit configured for mobility managementsuch as an Access and Mobility management Function, AMF, unit.

In another example, the network unit 10 of the higher generationwireless system 40 is a cloud-based network unit.

In a particular example, the control message is a security contextactivation procedure command.

For example, the control message may be a Non-Access Stratum, NAS,Security Mode Command, SMC, message.

As an example, the lower generation security algorithm(s) is/areselected based on the security capabilities of the wireless device inthe higher generation wireless system, which is a superset of thesecurity capabilities of the wireless device in the lower generationwireless system.

For example, information on the security capabilities of the wirelessdevice in the lower generation wireless system are included ininformation on the security capabilities of the wireless device in thehigher generation wireless system.

In a particular example, information on the security capabilities of thewireless device is received in a Registration Request in the highergeneration wireless system.

Optionally, the control message also includes information on selectedhigher generation security algorithm(s).

As an example, the higher generation wireless system 40 is a sourcesystem and the lower generation wireless system 50 is a target systemduring idle mode mobility.

In a first set of examples, the higher generation wireless system 40 isa 5G/NGS system and the lower generation wireless system 50 is a 4G/EPSsystem.

In a second set of alternative and/or complementary examples, the highergeneration wireless system 40 is a 5G/NGS system and the lowergeneration wireless system 50 is a 3G/UMTS system.

In a third set of examples, the higher generation wireless system 40 isa 4G/EPS system and the lower generation wireless system 50 is a 3G/UMTSsystem.

For 3G, the signaling protocol between the UE 30 and the core network isthe GPRS Mobility Management (GMM) with its GMM procedures; for 4G and5G it is called Non-Access Stratum (NAS).

By way of example, with reference to the example of FIG. 5C, the methodfurther comprises activating S4 NAS security and/or GMM security withthe lower generation wireless system 50 based on the stored selectedlower generation security algorithm(s) during idle mode mobility of thewireless communication device 30.

Optionally, with reference to the specific example of FIG. 5D, themethod further comprises sending S5 information to the wirelesscommunication device 30 indicating a security context to be used forintegrity protection of a Tracking Area Update, TAU, message.

For example, the information indicating a security context to be usedfor integrity protection of a TAU message may be sent together with theinformation on the selected lower generation security algorithm(s) inthe control message.

In a particular example, the information indicating a security contextto be used for integrity protection of a TAU message includesinformation indicating whether a higher generation security context or alower generation security context is to be used for integrity protectionof the TAU message.

Optionally, the method further comprises storing the informationindicating a security context to be used for integrity protection of aTAU message in the network unit.

The method may also involve sending the information on the selectedlower generation security algorithm(s) to a network unit, such as a MME,of the lower generation wireless system, e.g. for use in activating NASsecurity and/or GMM security.

For example, during idle mode mobility, upon the reception of a ContextRequest message from the target MME, the source AMF may derive a mappedEPS security context where the selected algorithms are based on the onestored and signaled during a NAS SMC with the UE. Similarly, the UEderives a mapped EPS security context such that the EPS algorithms areset based on the currently stored one that has been selected during aNAS SMC. The target MME activates NAS security immediately after thereception of the security context in the Context Response message.

More specifically, according to a second aspect, there is provided amethod, performed by a network unit, for supporting idle mode mobilityof a wireless communication device between different wirelesscommunication systems, including a higher generation wireless system anda lower generation wireless system.

With reference once again to FIG. 5B, the method basically comprises:

S1: selecting, in connection with a registration procedure and/or asecurity context activation procedure of the wireless communicationdevice with the higher generation wireless system, at least one securityalgorithm of the lower generation wireless system, also referred to aslower generation security algorithm(s);

S2: sending a control message including information on the selectedlower generation security algorithm(s) to the wireless communicationdevice; and

S3: storing information on the selected lower generation securityalgorithm(s) in the network unit.

Alternatively, the proposed technology is regarded as a method andcorresponding network unit for security algorithm selection forsupporting interworking between different wireless communicationsystems, including a higher generation wireless system and a lowergeneration wireless system.

By way of example, the control message may be a security contextactivation procedure command.

In a particular example, the control message is a Non-Access Stratum,NAS, Security Mode Command, SMC, message.

Optionally, the control message also includes information on selectedhigher generation security algorithm(s).

For example, the method is designed for supporting idle mode mobilityfrom a higher generation wireless system to a lower generation wirelesssystem.

In a particular example, the stored selected lower generation securityalgorithm(s) is/are used during idle mode mobility of the wirelesscommunication device to activate NAS security and/or GMM security withthe lower generation wireless system.

In a first set of examples, the higher generation wireless system is a5G/NGS system and the lower generation wireless system is a 4G/EPSsystem.

In a second set of alternative and/or complementary examples, the highergeneration wireless system is a 5G/NGS system and the lower generationwireless system is a 3G/UMTS system.

In a third set of examples, the higher generation wireless system is a4G/EPS system and the lower generation wireless system is a 3G/UMTSsystem.

FIG. 6A is a schematic flow diagram illustrating an example of a method,performed by a wireless communication device, for supportinginterworking between different wireless communication systems, includinga higher generation wireless system and a lower generation wirelesssystem, to enable secure communication for the wireless communicationdevice.

Basically, the method comprises:

S11: receiving, in connection with a registration procedure and/or asecurity context activation procedure of the wireless communicationdevice with the higher generation wireless system, a control messageincluding information on at least one security algorithm of the lowergeneration wireless system, also referred to as lower generationsecurity algorithm(s);

S12: storing information on the selected lower generation securityalgorithm(s) in the wireless communication device.

By way of example, the control message may be a security contextactivation procedure command.

In a particular example, the control message is a Non-Access Stratum,NAS, Security Mode Command, SMC, message.

Optionally, the method further comprises receiving informationindicating a security context to be used for integrity protection of aTracking Area Update, TAU, message.

Optionally, with reference to the example of FIG. 6B, the method furthercomprises storing S13 the information indicating a security context tobe used for integrity protection of a TAU message in the wirelesscommunication device 30.

For example, the information indicating a security context to be usedfor integrity protection of a TAU message may be received together withthe information on the selected lower generation security algorithm(s)in the control message.

In a first set of examples, the higher generation wireless system 40 isa 5G/NGS system and the lower generation wireless system 50 is a 4G/EPSsystem.

In a second set of alternative and/or complementary examples, the highergeneration wireless system 40 is a 5G/NGS system and the lowergeneration wireless system 50 is a 3G/UMTS system.

In a third set of examples, the higher generation wireless system 40 isa 4G/EPS system and the lower generation wireless system 50 is a 3G/UMTSsystem.

It should be understood that the proposed technology is generallyapplicable for supporting interworking between different generations ofwireless communication systems such as 5G, 4G and/or 3G, in differentcombinations. For example, as already mentioned, 5GS may supportinterworking with 4GS and/or 3GS, and it is possible to includeinformation on 4GS/EPS security algorithms and/or information on anyolder generation security algorithms such as 3GS security algorithms forany system generation that the network supports interworking with.

In the following, the proposed technology will be described withreference to a number of non-limiting examples in the context ofinterworking between 5GS/NGS and 4GS/EPS.

By way of example, it is proposed to signal the EPS algorithms to beused during interworking already during the NAS SMC procedure when theUE initially registers in the 5G System and establishes the NAS securitycontext. Therefore, there would be no need to use void values to triggera NAS SMC or to use a predefined standardized mapping table. Theselection is done at the AMF side based on the UE 5G securitycapabilities that are assumed to a be a superset of the UE EPS securitycapabilities and received in the Registration Request message. Theselected EPS algorithms are signaled in the NAS SMC alongside theselected 5G algorithms

Such a solution may provide one or more the following advantages:

-   -   It does not rely on a predefined standardized algorithm mapping        table that would require continuous updates to the standards        whenever new algorithms are introduced.    -   It does not misuse reserved algorithm values to force trigger a        NAS SMC.    -   It allows the activation of the NAS security context at the UE        and the target MME directly without a NAS SMC run.    -   It allows the independent evolutions of the EPS and 5GS security        algorithms.    -   It reuses the existing mechanism for secure algorithm        negotiation.

In a particular example, there is provided a security solution forinterworking between EPS and 5GS that removes the need for an activationprocedure run (NAS SMC) with the target system during idle mode mobilityfrom 5GS to EPS in order to negotiate and select the EPS algorithms tobe used with the target system, by mandating the selection of the EPSalgorithms already during security establishment in the source systemto, optionally based on local configuration, occur during the selectionand negotiation of the 5G security algorithms.

The support of the N26 interface of FIG. 4 which allows the exchange ofUE information including security between AMF and MME is optional.Therefore, interworking between EPS and 5GS using the N26 interface isoptional. In addition, in the interworking architecture of FIG. 4 ,since the MME and AMF are connected to the same HSS+/UDM node, thisindicates that all the nodes belong to the same operator network (ownerof the HSS). Consequently, interworking using the N26 interface is notonly optional, it is also an operator choice. Even if two differentoperators are still managing the MME and AMF, there would be agreementbetween the two parties to support and use the interface.

This suggests that whoever is managing the AMF, he could locallyconfigure any additional information required for the usage of the N26interface. Therefore, it would be logical to configure in advance theEPS algorithms to be used during idle mode mobility from 5GS to EPSusing the N26 interface. In case interworking is within the sameoperator network, then the operator would be aware of the MMEcapabilities and could configure the information in the AMF accordingly.Otherwise, it could be based on the agreement with another operator. Itcould be even configured randomly so that the UE gets the selection. Thetarget MME can always select other algorithms.

By way of example, it is proposed that based on its local configuration,the AMF optionally includes the EPS algorithms to be used solely duringinterworking with EPS. The selection of the EPS algorithms could bebased on the UE 5G security capabilities and a local configurationinformation for example a prioritized list of algorithms. Observe thathere it is assumed that the 5G security capabilities are a superset ofthe EPS security capabilities which in turn includes the previousgeneration security capabilities. The EPS selected algorithms aresignaled to the UE during the NAS SMC procedure which is typically runafter a successful primary authentication.

FIG. 7 is a schematic diagram illustrating an example of a NAS SMCprocedure with 4GS/EPS algorithm selection according to an embodiment.FIG. 7 includes the changes on top of the currently defined flow from TS33.501.

In step 0, the AMF selects the EPS algorithms as described above basedon local configuration and depending whether interworking using the N26interface is supported in this network or not. In step 1 a, integrityprotection is started. The selected EPS algorithms are included in theNAS Security Mode Command message from the AMF to the UE alongside theother security information as highlighted in step 1 b. In step 2 a, NASSMC integrity is verified and if successful, uplink ciphering, downlinkdeciphering and integrity protection are started. In step 2 b, the NASSecurity Mode Complete message is sent from the UE to the AMF, anddownlink ciphering is started in step 3. After a successful completionof the NAS SMC run, the selected EPS security algorithms are stored inthe UE and the AMF side as part of the UE security context in steps 4 aand 4 b.

FIG. 8 is a schematic diagram illustrating an example of usage ofpreselected 4GS/EPS algorithm(s) during idle mode mobility from 5GS/NGSto 4GS/EPS. FIG. 8 shows how the stored information is used during idlemode mobility to EPS to activate NAS security without a NAS SMC run.

Upon the reception of the Context Request message from the target MME,the source AMF derives a mapped EPS security context where the selectedalgorithms are based on the one stored and signaled during a NAS SMCwith the UE. Similarly, the UE derives a mapped EPS security contextsuch that the EPS algorithms are set based on the currently stored onethat has been selected during a NAS SMC. The target MME activates NASsecurity immediately after the reception of the security context in theContext Response message. The UE does the same possibly before or afterthe TAU message. The final TAU procedure message (the TAU Acceptmessage) would be then confidentiality and integrity protected. Observethat according to the legacy behavior, the target MME can alwaysinitiate a NAS SMC to select different algorithms before the TAU Acceptmessage.

In general, when a security context is available, the TAU message shallbe sent integrity protected. On the protection of the TAU message twosolutions were proposed. Solution (A) is based on using the 5G securitycontext to protect the TAU message. Solution (B) is based on using themapped EPS security context to protect the TAU message. Both solutionshave advantages and disadvantages.

For Solution (A), the upside is that the source AMF does not need tosupport other than the currently supported 5G NAS integrity algorithm.However, on the UE side, this solution is not legacy implementationfriendly since it would require changes to the EPS NAS implementation.For Solution (B), it is the other way around. Observe that for bothsolutions, unless the verification of the TAU message fails, the sourceAMF will have to send a mapped EPS security context to the target MME.

In this embodiment, it is proposed that an indication is optionally sentto the UE alongside the selected EPS algorithms to indicate whether theUE uses the mapped EPS security context or the 5G security context toprotect the TAU message.

FIG. 9 is a schematic diagram illustrating an example of a NAS SMCprocedure with TAU protection indication according to an embodiment.FIG. 9 shows the addition of the TAU Protection Indication(TP_Indication) to the NAS SMC procedure flow. This indication is storedin the UE as part of the 5G security context and at the AMF side as partof the UE security context.

FIG. 10 is a schematic diagram illustrating an example of usage of TAUprotection indication during idle mode mobility from 5GS/NGS to 4GS/EPS.FIG. 10 shows the usage of the indication during the mobility procedure.

This indication could be for example a Boolean flag that is, if set,indicates that the mapped EPS security context is to be used to protectthe TAU message, the 5G security context otherwise. During the TAUprocedure, the UE would check the stored TP_Indication to determinewhether to use the mapped EPS security context for the protection of theTAU message or not. The source AMF checks the TP_Indication as well todetermine whether it uses the mapped EPS context or the 5G securitycontext for the verification of the TAU message expected to be includedin the Context Request message from the target MME.

There are different possibilities related to the order of the derivationof the mapped EPS context and the checking of the indication steps. InFIG. 10 , the derivation of the mapped EPS security context step can beperformed before or after the TAU message transmission. In anotherembodiment, the UE can always start by deriving the mapped EPS securitycontext, then checking the TP_Indication.

It will be appreciated that the methods and arrangements describedherein can be implemented, combined and re-arranged in a variety ofways.

For example, embodiments may be implemented in hardware, or in softwarefor execution by suitable processing circuitry, or a combinationthereof.

The steps, functions, procedures, modules and/or blocks described hereinmay be implemented in hardware using any conventional technology, suchas discrete circuit or integrated circuit technology, including bothgeneral-purpose electronic circuitry and application-specific circuitry.

Alternatively, or as a complement, at least some of the steps,functions, procedures, modules and/or blocks described herein may beimplemented in software such as a computer program for execution bysuitable processing circuitry such as one or more processors orprocessing units.

Examples of processing circuitry includes, but is not limited to, one ormore microprocessors, one or more Digital Signal Processors (DSPs), oneor more Central Processing Units (CPUs), video acceleration hardware,and/or any suitable programmable logic circuitry such as one or moreField Programmable Gate Arrays (FPGAs), or one or more ProgrammableLogic Controllers (PLCs).

It should also be understood that it may be possible to re-use thegeneral processing capabilities of any conventional device or unit inwhich the proposed technology is implemented. It may also be possible tore-use existing software, e.g. by reprogramming of the existing softwareor by adding new software components.

According to an aspect, there is provided a network unit configured tosupport interworking between different wireless communication systems,including a higher generation wireless system and a lower generationwireless system, to enable secure communication with a wirelesscommunication device,

wherein the network unit is configured to select, in connection with aregistration procedure and/or a security context activation procedure ofthe wireless communication device with the higher generation wirelesssystem, at least one security algorithm of the lower generation wirelesssystem, also referred to as lower generation security algorithm(s);

wherein the network unit is configured to send a control messageincluding information on the selected lower generation securityalgorithm(s) to the wireless communication device; and

wherein the network unit is configured to store information on theselected lower generation security algorithm(s) in the network unit.

According to a similar aspect, there is also provided a network unitconfigured to support idle mode mobility of a wireless communicationdevice between different wireless communication systems, including ahigher generation wireless system and a lower generation wirelesssystem,

wherein the network unit is configured to select, in connection with aregistration procedure and/or a security context activation procedure ofthe wireless communication device with the higher generation wirelesssystem, at least one security algorithm of the lower generation wirelesssystem, also referred to as lower generation security algorithm(s);

wherein the network unit is configured to send a control messageincluding information on the selected lower generation securityalgorithm(s) to the wireless communication device; and

wherein the network unit is configured to store information on theselected lower generation security algorithm(s) in the network unit.

By way of example, the control message may be a security contextactivation procedure command.

In a particular example, the control message is a Non-Access Stratum,NAS, Security Mode Command, SMC, message.

For example, the network unit may be a network unit 10 of the highergeneration wireless system 40.

As an example, the network unit 10 is a core network unit configured formobility management.

In a particular example, the network unit 10 is an Access and Mobilitymanagement Function, AMF, unit.

By way of example, the network unit 10 is a network unit of a 5G/NGSsystem.

Alternatively, or complementary, the network unit 10 may be acloud-based network unit.

According to another aspect, there is provided a wireless communicationdevice configured to support interworking between different wirelesscommunication systems, including a higher generation wireless system anda lower generation wireless system, to enable secure communication forthe wireless communication device,

wherein the wireless communication device is configured to receive, inconnection with a registration procedure and/or a security contextactivation procedure of the wireless communication device with thehigher generation wireless system, a control message includinginformation on at least one security algorithm of the lower generationwireless system, also referred to as lower generation securityalgorithm(s);

wherein the wireless communication device is configured to storeinformation on the selected lower generation security algorithm(s) inthe wireless communication device.

By way of example, the control message may be a security contextactivation procedure command

In a particular example, the control message is a Non-Access Stratum,NAS, Security Mode Command, SMC, message.

FIG. 11A is a schematic block diagram illustrating an example of anarrangement such as a network unit and/or wireless communication deviceconfigured to support interworking between different wirelesscommunication systems according to an embodiment.

In this particular example, the arrangement 100 comprises a processor101 and a memory 102, the memory 102 comprising instructions executableby the processor 101, whereby the processor is operative to perform thefunctions described herein, e.g. to support interworking and/or idlemode mobility between different wireless communication systems managesecurity contexts at idle mode mobility.

Optionally, the arrangement 100 may also include an input/output (I/O)unit 103. The I/O unit 103 may include functions for wired and/orwireless communication with other devices and/or network nodes in thenetwork. In a particular example, the I/O unit 103 may be based on radiocircuitry for communication with one or more other nodes, includingtransmitting and/or receiving information. The I/O unit 103 may beinterconnected to the processor 101 and/or memory 102. By way ofexample, the I/O unit 103 may include any of the following: a receiver,a transmitter, a transceiver, input port(s) and/or output port(s).

FIG. 11B is a schematic block diagram illustrating an example of anarrangement such as a network unit and/or a wireless communicationdevice configured to support interworking between different wirelesscommunication systems according to another embodiment.

In this example, the arrangement 110 is based on a hardware circuitryimplementation. Particular examples of suitable hardware circuitryinclude one or more suitably configured or possibly reconfigurableelectronic circuitry, e.g., Application Specific Integrated Circuits(ASICs), FPGAs, or any other hardware logic such as circuits based ondiscrete logic gates and/or flip-flops interconnected to performspecialized functions in connection with suitable registers (REG),and/or memory units (MEM).

FIG. 11C is a schematic block diagram illustrating an example of anarrangement such as a network unit and/or wireless communication deviceconfigured to support interworking between different wirelesscommunication systems according to yet another embodiment.

In this example, the arrangement 120 is based on combination of bothprocessor(s) 122, 123 and hardware circuitry 124, 125 in connection withsuitable memory unit(s) 121. The arrangement 120 comprises one or moreprocessors 122, 123, memory 121 including storage for software (SW) anddata, and one or more units of hardware circuitry 124, 125. The overallfunctionality is thus partitioned between programmed software forexecution on one or more processors 122, 123, and one or morepre-configured or possibly reconfigurable hardware circuits 124, 125.The actual hardware-software partitioning can be decided by a systemdesigner based on a number of factors including processing speed, costof implementation and other requirements.

FIG. 12 is a schematic diagram illustrating an example of acomputer-implementation 200 according to an embodiment. In thisparticular example, at least some of the steps, functions, procedures,modules and/or blocks described herein are implemented in a computerprogram 225; 235, which is loaded into the memory 220 for execution byprocessing circuitry including one or more processors 210. Theprocessor(s) 210 and memory 220 are interconnected to each other toenable normal software execution. An optional input/output device 240may also be interconnected to the processor(s) 210 and/or the memory 220to enable input and/or output of relevant data such as inputparameter(s) and/or resulting output parameter(s).

The term ‘processor’ should be interpreted in a general sense as anysystem or device capable of executing program code or computer programinstructions to perform a particular processing, determining orcomputing task.

The processing circuitry including one or more processors 210 is thusconfigured to perform, when executing the computer program 225,well-defined processing tasks such as those described herein.

The processing circuitry does not have to be dedicated to only executethe above-described steps, functions, procedure and/or blocks, but mayalso execute other tasks.

In a particular embodiment, the computer program 225; 235 comprisesinstructions, which when executed by at least one processor 210, causethe processor(s) 210 to perform the actions described herein.

According to a particular aspect, there is provided a computer program225; 235 for supporting, when executed by a processor 210, interworkingbetween different wireless communication systems, including a highergeneration wireless system and a lower generation wireless system, toenable secure communication with a wireless communication device,wherein the computer program 225; 235 comprises instructions, which whenexecuted by the processor 210, cause the processor 210 to:

select, in connection with a registration procedure and/or a securitycontext activation procedure of the wireless communication device withthe higher generation wireless system, at least one security algorithmof the lower generation wireless system, also referred to as lowergeneration security algorithm(s);

generate a control message including information on the selected lowergeneration security algorithm(s) for transmission to the wirelesscommunication device; and

store information on the selected lower generation securityalgorithm(s).

According to yet another aspect, there is provided a computer programproduct comprising a computer-readable medium 220; 230 in which acomputer program 225; 235 of the above aspect is carried or stored.

According to another aspect, there is provided a computer program 225;235 for supporting, when executed by a processor 210, interworkingbetween different wireless communication systems, including a highergeneration wireless system and a lower generation wireless system, toenable secure communication for a wireless communication device, whereinthe computer program 225; 235 comprises instructions, which whenexecuted by the processor 210, cause the processor 210 to:

receive, in connection with a registration procedure and/or a securitycontext activation procedure of the wireless communication device withthe higher generation wireless system, a control message includinginformation on at least one security algorithm of the lower generationwireless system, also referred to as lower generation securityalgorithm(s);

store information on the selected lower generation security algorithm(s)in the wireless communication device.

According to still another aspect, there is provided a computer programproduct comprising a computer-readable medium 220; 230 in which acomputer program 225; 235 of the above aspect is carried or stored.

The proposed technology also provides a carrier comprising the computerprogram, wherein the carrier is one of an electronic signal, an opticalsignal, an electromagnetic signal, a magnetic signal, an electricsignal, a radio signal, a microwave signal, or a computer-readablestorage medium.

By way of example, the software or computer program 225; 235 may berealized as a computer program product, which is normally carried orstored on a computer-readable medium 220; 230, in particular anon-volatile medium. The computer-readable medium may include one ormore removable or non-removable memory devices including, but notlimited to a Read-Only Memory (ROM), a Random Access Memory (RAM), aCompact Disc (CD), a Digital Versatile Disc (DVD), a Blu-ray disc, aUniversal Serial Bus (USB) memory, a Hard Disk Drive (HDD) storagedevice, a flash memory, a magnetic tape, or any other conventionalmemory device. The computer program may thus be loaded into theoperating memory of a computer or equivalent processing device forexecution by the processing circuitry thereof.

The flow diagram or diagrams presented herein may be regarded as acomputer flow diagram or diagrams, when performed by one or moreprocessors. A corresponding apparatus may be defined as a group offunction modules, where each step performed by the processor correspondsto a function module. In this case, the function modules are implementedas a computer program running on the processor.

The computer program residing in memory may thus be organized asappropriate function modules configured to perform, when executed by theprocessor, at least part of the steps and/or tasks described herein.

FIG. 13 is a schematic diagram illustrating an example of an apparatusfor supporting interworking between different wireless communicationsystems, including a higher generation wireless system and a lowergeneration wireless system, to enable secure communication with awireless communication device. The apparatus 300 comprises:

a selection module 310 for selecting, in connection with a registrationprocedure and/or a security context activation procedure of the wirelesscommunication device with the higher generation wireless system, atleast one security algorithm of the lower generation wireless system,also referred to as lower generation security algorithm(s);

a generating module 320 for generating a control message includinginformation on the selected lower generation security algorithm(s) fortransmission to the wireless communication device; and

a storage module 330 for storing information on the selected lowergeneration security algorithm(s) in the network unit.

FIG. 14 is a schematic diagram illustrating an example of an apparatusfor supporting interworking between different wireless communicationsystems, including a higher generation wireless system and a lowergeneration wireless system, to enable secure communication for awireless communication device. The apparatus 400 comprises:

a receiving module 410 for receiving, in connection with a registrationprocedure and/or a security context activation procedure of the wirelesscommunication device with the higher generation wireless system, acontrol message including information on at least one security algorithmof the lower generation wireless system, also referred to as lowergeneration security algorithm(s);

a storage module 420 for storing information on the selected lowergeneration security algorithm(s) in the wireless communication device.

Alternatively it is possible to realize the module(s) in FIG. 13 and/orFIG. 14 predominantly by hardware modules, or alternatively by hardware,with suitable interconnections between relevant modules. Particularexamples include one or more suitably configured digital signalprocessors and other known electronic circuits, e.g. discrete logicgates interconnected to perform a specialized function, and/orApplication Specific Integrated Circuits (ASICs) as previouslymentioned. Other examples of usable hardware include input/output (I/O)circuitry and/or circuitry for receiving and/or sending signals. Theextent of software versus hardware is purely implementation selection.

For example, a so-called virtual apparatus may comprise processingcircuitry, which may include one or more microprocessor ormicrocontrollers, as well as other digital hardware, which may includedigital signal processors (DSPs), special-purpose digital logic, and thelike. The processing circuitry may be configured to execute program codestored in memory, which may include one or several types of memory suchas read-only memory (ROM), random-access memory, cache memory, flashmemory devices, optical storage devices, etc. Program code stored inmemory includes program instructions for executing one or moretelecommunications and/or data communications protocols as well asinstructions for carrying out one or more of the techniques describedherein, in several embodiments.

The term module or unit may have conventional meaning in the field ofelectronics, electrical devices and/or electronic devices and mayinclude, for example, electrical and/or electronic circuitry, devices,modules, processors, memories, logic solid state and/or discretedevices, computer programs or instructions for carrying out respectivetasks, procedures, computations, outputs, and/or displaying functions,and so on, as such as those that are described herein.

The proposed technology is generally applicable to management ofsecurity contexts in wireless communications. The proposed technologymay be applied to many specific applications and communication scenariosincluding secure communication within wireless networks, securelyproviding various services within such networks, including so-calledOver-the-Top (OTT) services. For example, the proposed technology mayprovide the underlying security for secure communication, and enablesand/or includes transfer and/or transmission and/or reception ofrelevant user data and/or control data in wireless communications.

In a complementary aspect, the proposed technology relates to a method,performed by a wireless device, further involving providing user data,and forwarding the user data to a host computer via the transmission toa network node.

In another complementary aspect, the proposed technology relates to acorresponding wireless device comprising processing circuitry configuredto perform any of the steps of such a method.

In yet another complementary aspect, the proposed technology relates toa method, performed by a network node, further involving obtaining userdata, and forwarding the user data to a host computer or a wirelessdevice.

In still another complementary aspect, the proposed technology relatesto a corresponding network node such as a base station comprisingprocessing circuitry configured to perform any of the steps of such amethod.

The proposed technology may also relate to a corresponding communicationsystem including a host computer and/or a wireless device and/or anetwork node.

It is also becoming increasingly popular to provide computing services(hardware and/or software) in network devices such as network nodesand/or servers where the resources are delivered as a service to remotelocations over a network. By way of example, this means thatfunctionality, as described herein, can be distributed or re-located toone or more separate physical nodes or servers. The functionality may bere-located or distributed to one or more jointly acting physical and/orvirtual machines that can be positioned in separate physical node(s),i.e. in the so-called cloud. This is sometimes also referred to as cloudcomputing, which is a model for enabling ubiquitous on-demand networkaccess to a pool of configurable computing resources such as networks,servers, storage, applications and general or customized services.

There are different forms of virtualization that can be useful in thiscontext, including one or more of:

Consolidation of network functionality into virtualized software runningon customized or generic hardware. This is sometimes referred to asnetwork function virtualization.

Co-location of one or more application stacks, including operatingsystem, running on separate hardware onto a single hardware platform.This is sometimes referred to as system virtualization, or platformvirtualization.

Co-location of hardware and/or software resources with the objective ofusing some advanced domain level scheduling and coordination techniqueto gain increased system resource utilization. This is sometimesreferred to as resource virtualization, or centralized and coordinatedresource pooling.

Although it may often desirable to centralize functionality in so-calledgeneric data centers, in other scenarios it may in fact be beneficial todistribute functionality over different parts of the network.

A Network Device (ND) may generally be seen as an electronic devicebeing communicatively connected to other electronic devices in thenetwork.

By way of example, the network device may be implemented in hardware,software or a combination thereof. For example, the network device maybe a special-purpose network device or a general purpose network device,or a hybrid thereof.

A special-purpose network device may use custom processing circuits anda proprietary operating system (OS), for execution of software toprovide one or more of the features or functions disclosed herein.

A general purpose network device may use common off-the-shelf (COTS)processors and a standard OS, for execution of software configured toprovide one or more of the features or functions disclosed herein.

By way of example, a special-purpose network device may include hardwarecomprising processing or computing resource(s), which typically includea set of one or more processors, and physical network interfaces (NIs),which sometimes are called physical ports, as well as non-transitorymachine readable storage media having stored thereon software. Aphysical NI may be seen as hardware in a network device through which anetwork connection is made, e.g. wirelessly through a wireless networkinterface controller (WNIC) or through plugging in a cable to a physicalport connected to a network interface controller (NIC). Duringoperation, the software may be executed by the hardware to instantiate aset of one or more software instance(s). Each of the softwareinstance(s), and that part of the hardware that executes that softwareinstance, may form a separate virtual network element.

By way of another example, a general purpose network device may forexample include hardware comprising a set of one or more processor(s),often COTS processors, and network interface controller(s) (NICs), aswell as non-transitory machine readable storage media having storedthereon software. During operation, the processor(s) executes thesoftware to instantiate one or more sets of one or more applications.While one embodiment does not implement virtualization, alternativeembodiments may use different forms of virtualization—for examplerepresented by a virtualization layer and software containers. Forexample, one such alternative embodiment implements operatingsystem-level virtualization, in which case the virtualization layerrepresents the kernel of an operating system (or a shim executing on abase operating system) that allows for the creation of multiple softwarecontainers that may each be used to execute one of a sets ofapplications. In an example embodiment, each of the software containers(also called virtualization engines, virtual private servers, or jails)is a user space instance (typically a virtual memory space). These userspace instances may be separate from each other and separate from thekernel space in which the operating system is executed; the set ofapplications running in a given user space, unless explicitly allowed,cannot access the memory of the other processes. Another suchalternative embodiment implements full virtualization, in which case: 1)the virtualization layer represents a hypervisor (sometimes referred toas a Virtual Machine Monitor (VMM)) or the hypervisor is executed on topof a host operating system; and 2) the software containers eachrepresent a tightly isolated form of software container called a virtualmachine that is executed by the hypervisor and may include a guestoperating system.

A hypervisor is the software/hardware that is responsible for creatingand managing the various virtualized instances and in some cases theactual physical hardware. The hypervisor manages the underlyingresources and presents them as virtualized instances. What thehypervisor virtualizes to appear as a single processor may actuallycomprise multiple separate processors. From the perspective of theoperating system, the virtualized instances appear to be actual hardwarecomponents.

A virtual machine is a software implementation of a physical machinethat runs programs as if they were executing on a physical,non-virtualized machine; and applications generally do not know they arerunning on a virtual machine as opposed to running on a “bare metal”host electronic device, though some systems provide para-virtualizationwhich allows an operating system or application to be aware of thepresence of virtualization for optimization purposes.

The instantiation of the one or more sets of one or more applications aswell as the virtualization layer and software containers if implemented,are collectively referred to as software instance(s). Each set ofapplications, corresponding software container if implemented, and thatpart of the hardware that executes them (be it hardware dedicated tothat execution and/or time slices of hardware temporally shared bysoftware containers), forms a separate virtual network element(s).

The virtual network element(s) may perform similar functionalitycompared to Virtual Network Element(s) (VNEs). This virtualization ofthe hardware is sometimes referred to as Network Function Virtualization(NFV)). Thus, NFV may be used to consolidate many network equipmenttypes onto industry standard high volume server hardware, physicalswitches, and physical storage, which could be located in data centers,NDs, and Customer Premise Equipment (CPE). However, differentembodiments may implement one or more of the software container(s)differently. For example, while embodiments are illustrated with eachsoftware container corresponding to a VNE, alternative embodiments mayimplement this correspondence or mapping between software container-VNEat a finer granularity level; it should be understood that thetechniques described herein with reference to a correspondence ofsoftware containers to VNEs also apply to embodiments where such a finerlevel of granularity is used.

According to yet another embodiment, there is provided a hybrid networkdevice, which includes both custom processing circuitry/proprietary OSand COTS processors/standard OS in a network device, e.g. in a card orcircuit board within a network device ND. In certain embodiments of sucha hybrid network device, a platform Virtual Machine (VM), such as a VMthat implements functionality of a special-purpose network device, couldprovide for para-virtualization to the hardware present in the hybridnetwork device.

FIG. 15 is a schematic diagram illustrating an example of howfunctionality can be distributed or partitioned between differentnetwork devices in a general case. In this example, there are at leasttwo individual, but interconnected network devices 501, 502, which mayhave different functionalities, or parts of the same functionality,partitioned between the network devices 501, 502. There may beadditional network devices 503 being part of such a distributedimplementation. The network devices 501, 502, 503 may be part of thesame wireless or wired communication system, or one or more of thenetwork devices may be so-called cloud-based network devices locatedoutside of the wireless or wired communication system.

In the following, a set of illustrative non-limiting examples will nowbe described with reference to FIGS. 16-22 .

FIG. 16 is a schematic diagram illustrating an example of a wirelessnetwork in accordance with some embodiments.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 16 .For simplicity, the wireless network of FIG. 16 only depicts networkQQ106, network nodes QQ160 and QQ160 b, and WDs QQ110, QQ110 b, andQQ110 c. In practice, a wireless network may further include anyadditional elements suitable to support communication between wirelessdevices or between a wireless device and another communication device,such as a landline telephone, a service provider, or any other networknode or end device. Of the illustrated components, network node QQ160and wireless device (WD) QQ110 are depicted with additional detail. Thewireless network may provide communication and other types of servicesto one or more wireless devices to facilitate the wireless devices'access to and/or use of the services provided by, or via, the wirelessnetwork.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 16 , network node QQ160 includes processing circuitry QQ170,device readable medium QQ180, interface QQ190, auxiliary equipmentQQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.Although network node QQ160 illustrated in the example wireless networkof FIG. 16 may represent a device that includes the illustratedcombination of hardware components, other embodiments may comprisenetwork nodes with different combinations of components. It is to beunderstood that a network node comprises any suitable combination ofhardware and/or software needed to perform the tasks, features,functions and methods disclosed herein. Moreover, while the componentsof network node QQ160 are depicted as single boxes located within alarger box, or nested within multiple boxes, in practice, a network nodemay comprise multiple different physical components that make up asingle illustrated component (e.g., device readable medium QQ180 maycomprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node QQ160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node QQ160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium QQ180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna QQ162 may be shared by the RATs). Network node QQ160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node QQ160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node QQ160.

Processing circuitry QQ170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry QQ170 may include processinginformation obtained by processing circuitry QQ170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode QQ160 components, such as device readable medium QQ180, networknode QQ160 functionality. For example, processing circuitry QQ170 mayexecute instructions stored in device readable medium QQ180 or in memorywithin processing circuitry QQ170. Such functionality may includeproviding any of the various wireless features, functions, or benefitsdiscussed herein. In some embodiments, processing circuitry QQ170 mayinclude a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or moreof radio frequency (RF) transceiver circuitry QQ172 and basebandprocessing circuitry QQ174. In some embodiments, radio frequency (RF)transceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry QQ170executing instructions stored on device readable medium QQ180 or memorywithin processing circuitry QQ170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry QQ170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry QQ170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry QQ170 alone or toother components of network node QQ160, but are enjoyed by network nodeQQ160 as a whole, and/or by end users and the wireless networkgenerally.

Device readable medium QQ180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry QQ170. Device readable medium QQ180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ170 and, utilized by network node QQ160.Device readable medium QQ180 may be used to store any calculations madeby processing circuitry QQ170 and/or any data received via interfaceQQ190. In some embodiments, processing circuitry QQ170 and devicereadable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication ofsignalling and/or data between network node QQ160, network QQ106, and/orWDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s)QQ194 to send and receive data, for example to and from network QQ106over a wired connection. Interface QQ190 also includes radio front endcircuitry QQ192 that may be coupled to, or in certain embodiments a partof, antenna QQ162. Radio front end circuitry QQ192 comprises filtersQQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may beconnected to antenna QQ162 and processing circuitry QQ170. Radio frontend circuitry may be configured to condition signals communicatedbetween antenna QQ162 and processing circuitry QQ170. Radio front endcircuitry QQ192 may receive digital data that is to be sent out to othernetwork nodes or WDs via a wireless connection. Radio front endcircuitry QQ192 may convert the digital data into a radio signal havingthe appropriate channel and bandwidth parameters using a combination offilters QQ198 and/or amplifiers QQ196. The radio signal may then betransmitted via antenna QQ162. Similarly, when receiving data, antennaQQ162 may collect radio signals which are then converted into digitaldata by radio front end circuitry QQ192. The digital data may be passedto processing circuitry QQ170. In other embodiments, the interface maycomprise different components and/or different combinations ofcomponents.

In certain alternative embodiments, network node QQ160 may not includeseparate radio front end circuitry QQ192, instead, processing circuitryQQ170 may comprise radio front end circuitry and may be connected toantenna QQ162 without separate radio front end circuitry QQ192.Similarly, in some embodiments, all or some of RF transceiver circuitryQQ172 may be considered a part of interface QQ190. In still otherembodiments, interface QQ190 may include one or more ports or terminalsQQ194, radio front end circuitry QQ192, and RF transceiver circuitryQQ172, as part of a radio unit (not shown), and interface QQ190 maycommunicate with baseband processing circuitry QQ174, which is part of adigital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna QQ162 may becoupled to radio front end circuitry QQ190 and may be any type ofantenna capable of transmitting and receiving data and/or signalswirelessly. In some embodiments, antenna QQ162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antennaQQ162 may be separate from network node QQ160 and may be connectable tonetwork node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network nodeQQ160 with power for performing the functionality described herein.Power circuitry QQ187 may receive power from power source QQ186. Powersource QQ186 and/or power circuitry QQ187 may be configured to providepower to the various components of network node QQ160 in a form suitablefor the respective components (e.g., at a voltage and current levelneeded for each respective component). Power source QQ186 may either beincluded in, or external to, power circuitry QQ187 and/or network nodeQQ160. For example, network node QQ160 may be connectable to an externalpower source (e.g., an electricity outlet) via an input circuitry orinterface such as an electrical cable, whereby the external power sourcesupplies power to power circuitry QQ187. As a further example, powersource QQ186 may comprise a source of power in the form of a battery orbattery pack which is connected to, or integrated in, power circuitryQQ187. The battery may provide backup power should the external powersource fail. Other types of power sources, such as photovoltaic devices,may also be used.

Alternative embodiments of network node QQ160 may include additionalcomponents beyond those shown in FIG. 16 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node QQ160 may include user interface equipment to allow inputof information into network node QQ160 and to allow output ofinformation from network node QQ160. This may allow a user to performdiagnostic, maintenance, repair, and other administrative functions fornetwork node QQ160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interfaceQQ114, processing circuitry QQ120, device readable medium QQ130, userinterface equipment QQ132, auxiliary equipment QQ134, power source QQ136and power circuitry QQ137. WD QQ110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface QQ114. In certain alternative embodiments, antenna QQ111 maybe separate from WD QQ110 and be connectable to WD QQ110 through aninterface or port. Antenna QQ111, interface QQ114, and/or processingcircuitry QQ120 may be configured to perform any receiving ortransmitting operations described herein as being performed by a WD. Anyinformation, data and/or signals may be received from a network nodeand/or another WD. In some embodiments, radio front end circuitry and/orantenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitryQQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one ormore filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114is connected to antenna QQ111 and processing circuitry QQ120, and isconfigured to condition signals communicated between antenna QQ111 andprocessing circuitry QQ120. Radio front end circuitry QQ112 may becoupled to or a part of antenna QQ111. In some embodiments, WD QQ110 maynot include separate radio front end circuitry QQ112; rather, processingcircuitry QQ120 may comprise radio front end circuitry and may beconnected to antenna QQ111. Similarly, in some embodiments, some or allof RF transceiver circuitry QQ122 may be considered a part of interfaceQQ114. Radio front end circuitry QQ112 may receive digital data that isto be sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry QQ112 may convert the digital data into aradio signal having the appropriate channel and bandwidth parametersusing a combination of filters QQ118 and/or amplifiers QQ116. The radiosignal may then be transmitted via antenna QQ111. Similarly, whenreceiving data, antenna QQ111 may collect radio signals which are thenconverted into digital data by radio front end circuitry QQ112. Thedigital data may be passed to processing circuitry QQ120. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD QQ110components, such as device readable medium QQ130, WD QQ110functionality. Such functionality may include providing any of thevarious wireless features or benefits discussed herein. For example,processing circuitry QQ120 may execute instructions stored in devicereadable medium QQ130 or in memory within processing circuitry QQ120 toprovide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitryQQ120 of WD QQ110 may comprise a SOC. In some embodiments, RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be on separate chips or setsof chips. In alternative embodiments, part or all of baseband processingcircuitry QQ124 and application processing circuitry QQ126 may becombined into one chip or set of chips, and RF transceiver circuitryQQ122 may be on a separate chip or set of chips. In still alternativeembodiments, part or all of RF transceiver circuitry QQ122 and basebandprocessing circuitry QQ124 may be on the same chip or set of chips, andapplication processing circuitry QQ126 may be on a separate chip or setof chips. In yet other alternative embodiments, part or all of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be combined in the same chipor set of chips. In some embodiments, RF transceiver circuitry QQ122 maybe a part of interface QQ114. RF transceiver circuitry QQ122 maycondition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry QQ120 executing instructions stored on device readable mediumQQ130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry QQ120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry QQ120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry QQ120 alone or to other componentsof WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end usersand the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry QQ120, may include processinginformation obtained by processing circuitry QQ120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD QQ110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium QQ130 may be operable to store a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ120. Device readable medium QQ130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry QQ120. In someembodiments, processing circuitry QQ120 and device readable medium QQ130may be considered to be integrated.

User interface equipment QQ132 may provide components that allow for ahuman user to interact with WD QQ110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipmentQQ132 may be operable to produce output to the user and to allow theuser to provide input to WD QQ110. The type of interaction may varydepending on the type of user interface equipment QQ132 installed in WDQQ110. For example, if WD QQ110 is a smart phone, the interaction may bevia a touch screen; if WD QQ110 is a smart meter, the interaction may bethrough a screen that provides usage (e.g., the number of gallons used)or a speaker that provides an audible alert (e.g., if smoke isdetected). User interface equipment QQ132 may include input interfaces,devices and circuits, and output interfaces, devices and circuits. Userinterface equipment QQ132 is configured to allow input of informationinto WD QQ110, and is connected to processing circuitry QQ120 to allowprocessing circuitry QQ120 to process the input information. Userinterface equipment QQ132 may include, for example, a microphone, aproximity or other sensor, keys/buttons, a touch display, one or morecameras, a USB port, or other input circuitry. User interface equipmentQQ132 is also configured to allow output of information from WD QQ110,and to allow processing circuitry QQ120 to output information from WDQQ110. User interface equipment QQ132 may include, for example, aspeaker, a display, vibrating circuitry, a USB port, a headphoneinterface, or other output circuitry. Using one or more input and outputinterfaces, devices, and circuits, of user interface equipment QQ132, WDQQ110 may communicate with end users and/or the wireless network, andallow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD QQ110 may further comprise power circuitryQQ137 for delivering power from power source QQ136 to the various partsof WD QQ110 which need power from power source QQ136 to carry out anyfunctionality described or indicated herein. Power circuitry QQ137 mayin certain embodiments comprise power management circuitry. Powercircuitry QQ137 may additionally or alternatively be operable to receivepower from an external power source; in which case WD QQ110 may beconnectable to the external power source (such as an electricity outlet)via input circuitry or an interface such as an electrical power cable.Power circuitry QQ137 may also in certain embodiments be operable todeliver power from an external power source to power source QQ136. Thismay be, for example, for the charging of power source QQ136. Powercircuitry QQ137 may perform any formatting, converting, or othermodification to the power from power source QQ136 to make the powersuitable for the respective components of WD QQ110 to which power issupplied.

FIG. 17 is a schematic diagram illustrating an example of an embodimentof a UE in accordance with various aspects described herein. As usedherein, a user equipment or UE may not necessarily have a user in thesense of a human user who owns and/or operates the relevant device.Instead, a UE may represent a device that is intended for sale to, oroperation by, a human user but which may not, or which may notinitially, be associated with a specific human user (e.g., a smartsprinkler controller). Alternatively, a UE may represent a device thatis not intended for sale to, or operation by, an end user but which maybe associated with or operated for the benefit of a user (e.g., a smartpower meter). UE QQ2200 may be any UE identified by the 3^(rd)Generation Partnership Project (3GPP), including a NB-IoT UE, a machinetype communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200,as illustrated in FIG. 17 , is one example of a WD configured forcommunication in accordance with one or more communication standardspromulgated by the 3^(rd) Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG.17 is a UE, the components discussed herein are equally applicable to aWD, and vice-versa.

In FIG. 17 , UE QQ200 includes processing circuitry QQ201 that isoperatively coupled to input/output interface QQ205, radio frequency(RF) interface QQ209, network connection interface QQ211, memory QQ215including random access memory (RAM) QQ217, read-only memory (ROM)QQ219, and storage medium QQ221 or the like, communication subsystemQQ231, power source QQ233, and/or any other component, or anycombination thereof. Storage medium QQ221 includes operating systemQQ223, application program QQ225, and data QQ227. In other embodiments,storage medium QQ221 may include other similar types of information.Certain UEs may utilize all of the components shown in FIG. 17 , or onlya subset of the components. The level of integration between thecomponents may vary from one UE to another UE. Further, certain UEs maycontain multiple instances of a component, such as multiple processors,memories, transceivers, transmitters, receivers, etc.

In FIG. 17 , processing circuitry QQ201 may be configured to processcomputer instructions and data. Processing circuitry QQ201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry QQ201 may includetwo central processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface QQ205 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE QQ200 may be configured touse an output device via input/output interface QQ205. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE QQ200. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE QQ200 may be configured to use aninput device via input/output interface QQ205 to allow a user to captureinformation into UE QQ200. The input device may include atouch-sensitive or presence-sensitive display, a camera (e.g., a digitalcamera, a digital video camera, a web camera, etc.), a microphone, asensor, a mouse, a trackball, a directional pad, a trackpad, a scrollwheel, a smartcard, and the like. The presence-sensitive display mayinclude a capacitive or resistive touch sensor to sense input from auser. A sensor may be, for instance, an accelerometer, a gyroscope, atilt sensor, a force sensor, a magnetometer, an optical sensor, aproximity sensor, another like sensor, or any combination thereof. Forexample, the input device may be an accelerometer, a magnetometer, adigital camera, a microphone, and an optical sensor.

In FIG. 17 , RF interface QQ209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface QQ211 may beconfigured to provide a communication interface to network QQ243 a.Network QQ243 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network QQ243 a may comprise aWi-Fi network. Network connection interface QQ211 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface QQ211 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM QQ217 may be configured to interface via bus QQ202 to processingcircuitry QQ201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM QQ219may be configured to provide computer instructions or data to processingcircuitry QQ201. For example, ROM QQ219 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage mediumQQ221 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium QQ221 may be configured toinclude operating system QQ223, application program QQ225 such as a webbrowser application, a widget or gadget engine or another application,and data file QQ227. Storage medium QQ221 may store, for use by UEQQ200, any of a variety of various operating systems or combinations ofoperating systems.

Storage medium QQ221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium QQ221 may allow UE QQ200 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium QQ221, which may comprise adevice readable medium.

In FIG. 17 , processing circuitry QQ201 may be configured to communicatewith network QQ243 b using communication subsystem QQ231. Network QQ243a and network QQ243 b may be the same network or networks or differentnetwork or networks. Communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.QQ2,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter QQ233 and/or receiver QQ235 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter QQ233and receiver QQ235 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem QQ231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem QQ231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network QQ243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, networkQQ243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source QQ213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE QQ200 or partitioned acrossmultiple components of UE QQ200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystemQQ231 may be configured to include any of the components describedherein. Further, processing circuitry QQ201 may be configured tocommunicate with any of such components over bus QQ202. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitryQQ201 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry QQ201 and communication subsystem QQ231. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 18 is a schematic block diagram illustrating an example of avirtualization environment QQ300 in which functions implemented by someembodiments may be virtualized. In the present context, virtualizingmeans creating virtual versions of apparatuses or devices which mayinclude virtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments QQ300 hosted byone or more of hardware nodes QQ330. Further, in embodiments in whichthe virtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications QQ320(which may alternatively be called software instances, virtualappliances, network functions, virtual nodes, virtual network functions,etc.) operative to implement some of the features, functions, and/orbenefits of some of the embodiments disclosed herein. Applications QQ320are run in virtualization environment QQ300 which provides hardwareQQ330 comprising processing circuitry QQ360 and memory QQ390. MemoryQQ390 contains instructions QQ395 executable by processing circuitryQQ360 whereby application QQ320 is operative to provide one or more ofthe features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose orspecial-purpose network hardware devices QQ330 comprising a set of oneor more processors or processing circuitry QQ360, which may becommercial off-the-shelf (COTS) processors, dedicated ApplicationSpecific Integrated Circuits (ASICs), or any other type of processingcircuitry including digital or analog hardware components or specialpurpose processors. Each hardware device may comprise memory QQ390-1which may be non-persistent memory for temporarily storing instructionsQQ395 or software executed by processing circuitry QQ360. Each hardwaredevice may comprise one or more network interface controllers (NICs)QQ370, also known as network interface cards, which include physicalnetwork interface QQ380. Each hardware device may also includenon-transitory, persistent, machine-readable storage media QQ390-2having stored therein software QQ395 and/or instructions executable byprocessing circuitry QQ360. Software QQ395 may include any type ofsoftware including software for instantiating one or more virtualizationlayers QQ350 (also referred to as hypervisors), software to executevirtual machines QQ340 as well as software allowing it to executefunctions, features and/or benefits described in relation with someembodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer QQ350 or hypervisor. Differentembodiments of the instance of virtual appliance QQ320 may beimplemented on one or more of virtual machines QQ340, and theimplementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 toinstantiate the hypervisor or virtualization layer QQ350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer QQ350 may present a virtual operating platform thatappears like networking hardware to virtual machine QQ340.

As shown in FIG. 18 , hardware QQ330 may be a standalone network nodewith generic or specific components. Hardware QQ330 may comprise antennaQQ3225 and may implement some functions via virtualization.Alternatively, hardware QQ330 may be part of a larger cluster ofhardware (e.g. such as in a data center or customer premise equipment(CPE)) where many hardware nodes work together and are managed viamanagement and orchestration (MANO) QQ3100, which, among others,oversees lifecycle management of applications QQ320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine QQ340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines QQ340, and that part of hardware QQ330 that executes thatvirtual machine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines QQ340 on top of hardware networking infrastructureQQ330 and corresponds to application QQ320 in FIG. 18 .

In some embodiments, one or more radio units QQ3200 that each includeone or more transmitters QQ3220 and one or more receivers QQ3210 may becoupled to one or more antennas QQ3225. Radio units QQ3200 maycommunicate directly with hardware nodes QQ330 via one or moreappropriate network interfaces and may be used in combination with thevirtual components to provide a virtual node with radio capabilities,such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system QQ3230 which may alternatively be used for communicationbetween the hardware nodes QQ330 and radio units QQ3200.

FIG. 19 is a schematic diagram illustrating an example of atelecommunication network connected via an intermediate network to ahost computer in accordance with some embodiments.

With reference to FIG. 19 , in accordance with an embodiment, acommunication system includes telecommunication network QQ410, such as a3GPP-type cellular network, which comprises access network QQ411, suchas a radio access network, and core network QQ414. Access network QQ411comprises a plurality of base stations QQ412 a, QQ412 b, QQ412 c, suchas NBs, eNBs, gNBs or other types of wireless access points, eachdefining a corresponding coverage area QQ413 a, QQ413 b, QQ413 c. Eachbase station QQ412 a, QQ412 b, QQ412 c is connectable to core networkQQ414 over a wired or wireless connection QQ415. A first UE QQ491located in coverage area QQ413 c is configured to wirelessly connect to,or be paged by, the corresponding base station QQ412 c. A second UEQQ492 in coverage area QQ413 a is wirelessly connectable to thecorresponding base station QQ412 a. While a plurality of UEs QQ491,QQ492 are illustrated in this example, the disclosed embodiments areequally applicable to a situation where a sole UE is in the coveragearea or where a sole UE is connecting to the corresponding base stationQQ412.

Telecommunication network QQ410 is itself connected to host computerQQ430, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer QQ430 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections QQ421 and QQ422 between telecommunication network QQ410 andhost computer QQ430 may extend directly from core network QQ414 to hostcomputer QQ430 or may go via an optional intermediate network QQ420.Intermediate network QQ420 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network QQ420,if any, may be a backbone network or the Internet; in particular,intermediate network QQ420 may comprise two or more sub-networks (notshown).

The communication system of FIG. 19 as a whole enables connectivitybetween the connected UEs QQ491, QQ492 and host computer QQ430. Theconnectivity may be described as an over-the-top (OTT) connection QQ450.Host computer QQ430 and the connected UEs QQ491, QQ492 are configured tocommunicate data and/or signaling via OTT connection QQ450, using accessnetwork QQ411, core network QQ414, any intermediate network QQ420 andpossible further infrastructure (not shown) as intermediaries. OTTconnection QQ450 may be transparent in the sense that the participatingcommunication devices through which OTT connection QQ450 passes areunaware of routing of uplink and downlink communications. For example,base station QQ412 may not or need not be informed about the pastrouting of an incoming downlink communication with data originating fromhost computer QQ430 to be forwarded (e.g., handed over) to a connectedUE QQ491. Similarly, base station QQ412 need not be aware of the futurerouting of an outgoing uplink communication originating from the UEQQ491 towards the host computer QQ430.

FIG. 20 is a schematic diagram illustrating an example of a hostcomputer communicating via a base station with a user equipment over apartially wireless connection in accordance with some embodiments

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 20 . In communicationsystem QQ500, host computer QQ510 comprises hardware QQ515 includingcommunication interface QQ516 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of communication system QQ500. Host computer QQ510 furthercomprises processing circuitry QQ518, which may have storage and/orprocessing capabilities. In particular, processing circuitry QQ518 maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer QQ510further comprises software QQ511, which is stored in or accessible byhost computer QQ510 and executable by processing circuitry QQ518.Software QQ511 includes host application QQ512. Host application QQ512may be operable to provide a service to a remote user, such as UE QQ530connecting via OTT connection QQ550 terminating at UE QQ530 and hostcomputer QQ510. In providing the service to the remote user, hostapplication QQ512 may provide user data which is transmitted using OTTconnection QQ550.

Communication system QQ500 further includes base station QQ520 providedin a telecommunication system and comprising hardware QQ525 enabling itto communicate with host computer QQ510 and with UE QQ530. HardwareQQ525 may include communication interface QQ526 for setting up andmaintaining a wired or wireless connection with an interface of adifferent communication device of communication system QQ500, as well asradio interface QQ527 for setting up and maintaining at least wirelessconnection QQ570 with UE QQ530 located in a coverage area (not shown inFIG. 20 ) served by base station QQ520. Communication interface QQ526may be configured to facilitate connection QQ560 to host computer QQ510.Connection QQ560 may be direct or it may pass through a core network(not shown in FIG. 20 ) of the telecommunication system and/or throughone or more intermediate networks outside the telecommunication system.In the embodiment shown, hardware QQ525 of base station QQ520 furtherincludes processing circuitry QQ528, which may comprise one or moreprogrammable processors, application-specific integrated circuits, fieldprogrammable gate arrays or combinations of these (not shown) adapted toexecute instructions. Base station QQ520 further has software QQ521stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referredto. The hardware QQ535 may include radio interface QQ537 configured toset up and maintain wireless connection QQ570 with a base stationserving a coverage area in which UE QQ530 is currently located. HardwareQQ535 of UE QQ530 further includes processing circuitry QQ538, which maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. UE QQ530 furthercomprises software QQ531, which is stored in or accessible by UE QQ530and executable by processing circuitry QQ538. Software QQ531 includesclient application QQ532. Client application QQ532 may be operable toprovide a service to a human or non-human user via UE QQ530, with thesupport of host computer QQ510. In host computer QQ510, an executinghost application QQ512 may communicate with the executing clientapplication QQ532 via OTT connection QQ550 terminating at UE QQ530 andhost computer QQ510. In providing the service to the user, clientapplication QQ532 may receive request data from host application QQ512and provide user data in response to the request data. OTT connectionQQ550 may transfer both the request data and the user data. Clientapplication QQ532 may interact with the user to generate the user datathat it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530illustrated in FIG. 20 may be similar or identical to host computerQQ430, one of base stations QQ412 a, QQ412 b, QQ412 c and one of UEsQQ491, QQ492 of FIG. 19 , respectively. This is to say, the innerworkings of these entities may be as shown in FIG. 20 and independently,the surrounding network topology may be that of FIG. 19 .

In FIG. 20 , OTT connection QQ550 has been drawn abstractly toillustrate the communication between host computer QQ510 and UE QQ530via base station QQ520, without explicit reference to any intermediarydevices and the precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE QQ530 or from the service provider operating host computerQQ510, or both. While OTT connection QQ550 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE QQ530 using OTT connectionQQ550, in which wireless connection QQ570 forms the last segment.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection QQ550 between hostcomputer QQ510 and UE QQ530, in response to variations in themeasurement results. The measurement procedure and/or the networkfunctionality for reconfiguring OTT connection QQ550 may be implementedin software QQ511 and hardware QQ515 of host computer QQ510 or insoftware QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments,sensors (not shown) may be deployed in or in association withcommunication devices through which OTT connection QQ550 passes; thesensors may participate in the measurement procedure by supplying valuesof the monitored quantities exemplified above, or supplying values ofother physical quantities from which software QQ511, QQ531 may computeor estimate the monitored quantities. The reconfiguring of OTTconnection QQ550 may include message format, retransmission settings,preferred routing etc.; the reconfiguring need not affect base stationQQ520, and it may be unknown or imperceptible to base station QQ520.Such procedures and functionalities may be known and practiced in theart. In certain embodiments, measurements may involve proprietary UEsignaling facilitating host computer QQ510's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software QQ511 and QQ531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection QQ550 while it monitors propagation times, errors etc.

FIGS. 21A-B are schematic flow diagrams illustrating examples of methodsimplemented in a communication system including, e.g. a host computer,and optionally also a base station and a user equipment in accordancewith some embodiments.

FIG. 21A is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIG. 19 and FIG. 20 . Forsimplicity of the present disclosure, only drawing references to FIG.21A will be included in this section. In step QQ610, the host computerprovides user data. In substep QQ611 (which may be optional) of stepQQ610, the host computer provides the user data by executing a hostapplication. In step QQ620, the host computer initiates a transmissioncarrying the user data to the UE. In step QQ630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step QQ640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 21B is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIG. 19 and FIG. 20 . Forsimplicity of the present disclosure, only drawing references to FIG.21B will be included in this section. In step QQ710 of the method, thehost computer provides user data. In an optional substep (not shown) thehost computer provides the user data by executing a host application. Instep QQ720, the host computer initiates a transmission carrying the userdata to the UE. The transmission may pass via the base station, inaccordance with the teachings of the embodiments described throughoutthis disclosure. In step QQ730 (which may be optional), the UE receivesthe user data carried in the transmission.

FIGS. 22A-B are schematic diagrams illustrating examples of methodsimplemented in a communication system including a host computer, a basestation and a user equipment in accordance with some embodiments.

FIG. 22A is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIG. 19 and FIG. 20 . Forsimplicity of the present disclosure, only drawing references to FIG.22A will be included in this section. In step QQ810 (which may beoptional), the UE receives input data provided by the host computer.Additionally or alternatively, in step QQ820, the UE provides user data.In substep QQ821 (which may be optional) of step QQ820, the UE providesthe user data by executing a client application. In substep QQ811 (whichmay be optional) of step QQ810, the UE executes a client applicationwhich provides the user data in reaction to the received input dataprovided by the host computer. In providing the user data, the executedclient application may further consider user input received from theuser. Regardless of the specific manner in which the user data wasprovided, the UE initiates, in substep QQ830 (which may be optional),transmission of the user data to the host computer. In step QQ840 of themethod, the host computer receives the user data transmitted from theUE, in accordance with the teachings of the embodiments describedthroughout this disclosure.

FIG. 22B is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIG. 19 and FIG. 20 . Forsimplicity of the present disclosure, only drawing references to FIG.22B will be included in this section. In step QQ910 (which may beoptional), in accordance with the teachings of the embodiments describedthroughout this disclosure, the base station receives user data from theUE. In step QQ920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In stepQQ930 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

In the following, examples of illustrative and non-limiting embodimentswill be given:

There is provided a method performed by a network node such as a basestation as described herein.

Optionally, the method further comprises:

-   -   obtaining user data; and    -   forwarding the user data to a host computer or a wireless        device.

There is also provided a network node such as a base station comprisingprocessing circuitry configured to perform any of the steps of themethod described herein.

There is further provided a communication system including a hostcomputer comprising:

-   -   processing circuitry configured to provide user data; and    -   a communication interface configured to forward the user data to        a cellular network for transmission to a user equipment (UE),    -   wherein the cellular network comprises a base station having a        radio interface and processing circuitry, the base station's        processing circuitry configured to perform any of the steps of        the method described herein.

In a particular example embodiment, the communication system furtherincludes the base station.

In yet another example embodiment, the processing circuitry of the hostcomputer is configured to execute a host application, thereby providingthe user data; and the UE comprises processing circuitry configured toexecute a client application associated with the host application.

There is also provided a method implemented in a communication systemincluding a host computer, a base station and a user equipment (UE), themethod comprising:

-   -   at the host computer, providing user data; and    -   at the host computer, initiating a transmission carrying the        user data to the UE via a cellular network comprising the base        station, wherein the base station performs any of the steps of        the method described herein.

In a particular example embodiment, the method further comprises, at thebase station, transmitting the user data.

In yet another example embodiment, the user data is provided at the hostcomputer by executing a host application, and the method furthercomprises, at the UE, executing a client application associated with thehost application.

There is further provided a communication system including a hostcomputer comprising a communication interface configured to receive userdata originating from a transmission from a user equipment (UE) to abase station, wherein the base station comprises a radio interface andprocessing circuitry, the base station's processing circuitry configuredto perform any of the steps of the method described herein.

In a particular example, the communication system includes the basestation.

In yet another example embodiment, the communication system furtherincludes the UE, wherein the UE is configured to communicate with thebase station.

By way of example, the processing circuitry of the host computer may beconfigured to execute a host application; and the UE may be configuredto execute a client application associated with the host application,thereby providing the user data to be received by the host computer.

The embodiments described above are merely given as examples, and itshould be understood that the proposed technology is not limitedthereto. It will be understood by those skilled in the art that variousmodifications, combinations and changes may be made to the embodimentswithout departing from the present scope as defined by the appendedclaims. In particular, different part solutions in the differentembodiments can be combined in other configurations, where technicallypossible.

The invention claimed is:
 1. A method, performed by a network unit, forsupporting interworking between different wireless communicationsystems, including a higher generation wireless system and a lowergeneration wireless system, to enable secure communication with awireless communication device, wherein the method comprises: selecting,in connection with a registration procedure and/or a security contextactivation procedure of the wireless communication device with thehigher generation wireless system, at least one security algorithm ofthe lower generation wireless system, also referred to as lowergeneration security algorithm(s); sending a control message includinginformation on the selected lower generation security algorithm(s) tothe wireless communication device; and storing information on theselected lower generation security algorithm(s) in the network unit. 2.The method of claim 1, wherein the method is performed by a network unitof the higher generation wireless system when the wireless communicationdevice registers and initiates establishment of a security context withthe higher generation wireless system.
 3. The method of claim 2, whereinthe network unit of the higher generation wireless system is a corenetwork unit configured for mobility management, and/or a cloud-basednetwork unit.
 4. The method of claim 2, wherein the network unit of thehigher generation wireless system is an Access and Mobility managementFunction, AMF, unit.
 5. The method of claim 1, wherein the controlmessage is a security context activation procedure command.
 6. Themethod of claim 1, wherein the control message is a Non-Access Stratum,NAS, Security Mode Command, SMC, message.
 7. The method of claim 1,wherein the lower generation security algorithm(s) is/are selected basedon security capabilities of the wireless device in the higher generationwireless system, which is a superset of the security capabilities of thewireless device in the lower generation wireless system.
 8. The methodof claim 7, wherein information on the security capabilities of thewireless device in the lower generation wireless system is/are includedin information on the security capabilities of the wireless device inthe higher generation wireless system.
 9. The method of claim 7, whereininformation on the security capabilities of the wireless device isreceived in a Registration Request in the higher generation wirelesssystem.
 10. The method of claim 1, wherein the control message alsoincludes information on selected higher generation securityalgorithm(s).
 11. The method of claim 1, wherein the higher generationwireless system is a 5G/NGS system and the lower generation wirelesssystem is a 4G/EPS system, or the higher generation wireless system is a5G/NGS system and the lower generation wireless system is a 3G/UMTSsystem, or the higher generation wireless system is a 4G/EPS system andthe lower generation wireless system is a 3G/UMTS system.
 12. The methodof claim 1, further comprising activating Non-Access Stratum, NAS,security and/or GPRS Mobility Management, GMM, security with the lowergeneration wireless system based on the stored selected lower generationsecurity algorithm(s) during idle mode mobility of the wirelesscommunication device.
 13. The method of claim 1, wherein the methodfurther comprises sending information to the wireless communicationdevice indicating a security context to be used for integrity protectionof a Tracking Area Update, TAU, message.
 14. The method of claim 13,wherein the information indicating a security context to be used forintegrity protection of a TAU message is sent together with theinformation on the selected lower generation security algorithm(s) inthe control message.
 15. The method of claim 13, wherein the informationindicating a security context to be used for integrity protection of aTAU message includes information indicating whether a higher generationsecurity context or a lower generation security context is to be usedfor integrity protection of the TAU message.
 16. A method, performed bya wireless communication device, for supporting interworking betweendifferent wireless communication systems, including a higher generationwireless system and a lower generation wireless system, to enable securecommunication for the wireless communication device, wherein the methodcomprises: receiving, in connection with a security context activationprocedure of the wireless communication device with the highergeneration wireless system, a control message including information onat least one security algorithm of the lower generation wireless system,also referred to as lower generation security algorithm(s); storinginformation on the selected lower generation security algorithm(s) inthe wireless communication device.
 17. The method of claim 16, whereinthe control message is a security context activation procedure command.18. The method of claim 16, wherein the control message is a Non-AccessStratum, NAS, Security Mode Command, SMC, message.
 19. The method ofclaim 16, wherein the method further comprises receiving informationindicating a security context to be used for integrity protection of aTracking Area Update, TAU, message.
 20. The method of claim 16, whereinthe higher generation wireless system is a 5G/NGS system and the lowergeneration wireless system is a 4G/EPS system, or the higher generationwireless system is a 5G/NGS system and the lower generation wirelesssystem is a 3G/UMTS system, or the higher generation wireless system isa 4G/EPS system and the lower generation wireless system is a 3G/UMTSsystem.